home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Amiga Collections: Tampa Bay Amiga Group
/
TBAG - Tampa Bay Amiga Group's Disk of the Month #67 (1992)(Merlin's Software - Amiganuts United)(PD).zip
/
TBAG - Tampa Bay Amiga Group's Disk of the Month #67 (1992)(Merlin's Software - Amiganuts United)(PD).adf
/
Docs
/
optimizer.docs
< prev
next >
Wrap
Text File
|
1992-04-11
|
4KB
|
75 lines
Optimizer 1.25 A freeware product by Tim Stotelmeyer
This program will optimize hard disks, recoverable ram disks (rads), and
floppy disks, which use either the Fast File System (FFS) or the Old File
System (OFS). The AmigaDOS 2.04 HARD LINKs for both files and directories
are also supported. This program works with AmigaDOS versions 1.2 and above.
Where possible files are optimized such that the components of a file are
in one continuous block. Files optimized are optimized for reading.
Files and directories are placed in the order as seen when using the
AmigaDOS command "LIST." The contents of a subdirectory are placed after
the last file of the current directory. This speeds up the listing of
files in the current directory.
A note for using this program to optimize a floppy. It is faster if you
copy the disk to RAD: using "DISKCOPY," optimize RAD:, then use "DISKCOPY"
to copy from RAD: to your floppy.
As with any optimizer make a backup of the disk that you want optimized
in case of trouble.
After starting the program from either the Workbench or from the CLI, the
program will open its own high-res non-interlaced screen. The colors are
set to the current Workbench colors. At the bottom of the screen
are four buttons. They are "START," "SCAN," "DRIVE," and "EXIT." The
"START" button will start the optimization. Before a disk can be optimized
it must first be scanned. The "SCAN" button will cause the current disk to
be scanned. The "DRIVE" button will cycle through the drives that have a
disk in them. The field next to the "DRIVE" button shows the current drive.
The "EXIT" button is for exiting the program. During either a disk scan
or optimization, the "EXIT" button will change to "STOP" and will stop the
current action.
Above the buttons are five statistics, "FILES LEFT," "BLOCKS LEFT,"
"PERCENT DONE," "TIME," and "DONE AT." After a drive has been scanned
"FILES LEFT" will contain the number of files on the drive, and "BLOCKS LEFT"
will contain the number of blocks of data that are on the drive. Once
the optimization process has started, "FILES LEFT" and "BLOCKS LEFT" will
contain the number of files and data blocks that still need to be optimized,
respectfully. "PERCENT DONE" will contain the percentage of blocks optimized.
"TIME" will contain the current time of day for computer. "DONE AT" will
contain a continuously updated estimate of the time of day that the
optimization will be done. The first few estimates will not be very
accurate.
Above the statistics is a field, which if a disk had been scanned, will show
the layout of the disk. Workbench color 1 denotes continuous, unfragmented
blocks of data. Workbench color 2 denotes fragmented blocks of data.
If a drive had been optimized or partially optimized, clicking on the "EXIT"
button will cause a requester to pop up telling the user that
"A drive has been optimized. You should reboot for safety." The user can
click on "REBOOT" or "EXIT." Because of changes made in how AmigaDOS keeps
track of some files in version 2.04 of AmigaDOS, the Amiga needs to be
rebooted after a disk (usually the boot disk) has been optimized.
Even though, I have thoroughly tested this program, I cannot stress the need
for backing up your data. A lot of things can happen, that are outside the
scope of this program. So it's better to be safe than sorry. On this note,
I do not take responsibility for loss of data, or loss of revenue resulting
from the loss of data, due to the use of this program.
Changes:
1.25: Fixed bug with optimizing a disk just optimized without having
exited the program.
Hopefully, fixed a bug with disk partition sizes greater than 51 Meg.
Made interface look 2.0-ish.
1.2: Increased speed by at least a factor of 2.
Allow up to 72 data blocks to be moved at a time.
1.1: Internal version with some bug fixes.
1.0: First release.